Hi there,

So my situation is I have a Content DB that is over 100GB in SP 2010.  My plan is to "split" it when I move the Site Collection to SP 2013.  So what I have done so far is:-

1. Backup from SP 2010 environment;
2. Restore to SP 2013 (SQL 2012) environment;
3. Mount and upgrade Content DB to original URL - http://intranet/sites/Ops;
4. Tests okay in browser etc in SP 2013 version
5. Backup to a .bak file;
6. Delete content from the mounted DB that is no longer needed
7. Run the following command to restore to new URL and new Content DB

Restore-SPSite http://intranet/sites/NewURL -Path z:\SPS_Operations_7Apr1627.bak -ContentDatabase SPS_NewContenDB 

Unfortunately, I get the below errors in the log file

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	ki7k	High	Could not deserialize site from z:\SPS_Operations_27Apr1627.bak . System.ArgumentException: Version string portion was too short or too long.     at System.Version.TryParseVersion(String version, VersionResult& result)     at System.Version.Parse(String input)     at Microsoft.SharePoint.SPSite.Restore(String filename, Boolean isADMode, Boolean& readOnlyMode, Boolean& hadWriteLock)	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	8e11	High	Deleting the site at http://intranet/sites/NewURL and not deleting AD accounts.	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	88z7	Medium	SPRequest: Logging result 0xbd649260 from reInit	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	8e2s	Medium	Unknown SPRequest error occurred. More information: 0x80070003	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	72k4	Medium	<nativehr>0x80070003</nativehr><nativestack></nativestack>	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	8kh7	High	<nativehr>0x80070003</nativehr><nativestack></nativestack>	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	aix9j	High	SPRequest.GetSiteFlags: UserPrincipalName=i:0).w|s-1-5-21-112552688-835663071-165283079-57096, AppPrincipalName= ,bstrUrl=http://intranet/sites/NewURL	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	General	ai1wu	Medium	System.IO.DirectoryNotFoundException: <nativehr>0x80070003</nativehr><nativestack></nativestack>, StackTrace:    at Microsoft.SharePoint.SPSite.Delete(SPSiteDeleteFlags flags)     at Microsoft.SharePoint.SPSite.Restore(String filename, Boolean isADMode, Boolean& readOnlyMode, Boolean& hadWriteLock)     at Microsoft.SharePoint.Administration.SPSiteCollection.Restore(String strSiteUrl, String strFilename, Boolean bOverwrite, Boolean bGradualDelete, Boolean hostHeaderAsSiteName, Boolean preserveSiteId)     at Microsoft.SharePoint.PowerShell.SPCmdletRestoreSite.InternalProcessRecord()     at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()     at System.Management.Automation.CommandProcessor.ProcessRecord()     at System.Management.Automation.CommandProcessorBase.DoExecute()     at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)     at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)     at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)     at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)     at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)     at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame)     at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0)     at System.Management.Automation.DlrScriptCommandProcessor.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess)     at System.Management.Automation.CommandProcessorBase.DoComplete()     at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProcessorBase commandRequestingUpstreamCommandsToStop)     at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)     at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()     at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()     at System.Management.Automation.Runspaces.PipelineThread.WorkerProc()     at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)     at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)     at System.Threading.ThreadHelper.ThreadStart()	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	PowerShell	6tf2	High	System.IO.DirectoryNotFoundException: <nativehr>0x80070003</nativehr><nativestack></nativestack>     at Microsoft.SharePoint.Library.SPRequestInternalClass.GetSiteFlags(String bstrUrl)     at Microsoft.SharePoint.Library.SPRequest.GetSiteFlags(String bstrUrl)     at Microsoft.SharePoint.SPSite.Delete(SPSiteDeleteFlags flags)     at Microsoft.SharePoint.SPSite.Restore(String filename, Boolean isADMode, Boolean& readOnlyMode, Boolean& hadWriteLock)     at Microsoft.SharePoint.Administration.SPSiteCollection.Restore(String strSiteUrl, String strFilename, Boolean bOverwrite, Boolean bGradualDelete, Boolean hostHeaderAsSiteName, Boolean preserveSiteId)     at Microsoft.SharePoint.PowerShell.SPCmdletRestoreSite.InternalProcessRecord()     at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord()	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

04/28/2015 15:41:34.80	PowerShell.exe (0x474C)	0x25DC	SharePoint Foundation	PowerShell	91ux	High	Error Category: InvalidData    Target Object  Microsoft.SharePoint.PowerShell.SPCmdletRestoreSite  Details  NULL  RecommendedAction NULL	ccf46a6a-0ee0-4ce1-b4cb-8113bc011943

I have run the config wizard and it finished successfully.  The DB's are all the same version, servers are not in need of an upgrade. 

Any ideas?

*Update* 

After banging my head (and Mr Google"s) against the wall, I decided to try a backup of the Site Collection again.  The first time, my DBA had backed up the DB straight from SQL.  This time, I ran the powershell:-

Backup-SPSite http://intranet/sites/Ops Path E:\Backup\OpsBackup.bak -UseSqlSnapshot

The DB is quite large - 120GB in fact and it took about 4-5 hours to backup. I am now currently restoring with no errors as yet. Fingers crossed.

I'll post an update tomorrow when hopefully it has finished.

Hi,

According to your description, my understanding is that there are several errors after you split Content DB.

Before you split Content DB, you need to create a new content database in web application. The content database should be mapped to web application.

More details about how to split content database:

http://kancharla-sharepoint.blogspot.com/2013/07/sharepoint-split-content-database.html

In addition, a solution to split content database can be to move site collections between databases.

An article about how to move site collections between databases in SharePoint 2013:

https://technet.microsoft.com/en-us/library/cc825328.aspx?f=255&MSPPError=-2147217396

Best Regards,

Dean Wang

Hi Dean,

Thanks for your suggestions.  The original Content DB only has one site collection (with four subsites) - it have just been left to grow unfortunately.  So, move site collections between DB's is not an option.  Exporting and importing is not an option was we need to keep the workflow history on several lists/libraries.

So, I started again.  The current site collection is complete - hasn't been split.  So I backed it up to a .bak file and then ran Restore-spsite pointing to a new URL and new ContentDB.  I appears to be restoring and then the <nativehr>.... error.

Anybody?

Hi kelsnz,

Please make sure the .bak file SharePoint server version is the same as the restore server version.

Please make sure the used user account have the permission on the content DB for the web application that you want to restore on.

Best Regards,

Dean Wang

Hi Dean,

I am backing up and restoring to the same server so there should not be any version issues.  The account I am using to run the Restore-SPSite powershell is an SQL sys_admin and its also a farm administrator so permissions are not an issue either.

I tried yesterday a backup omitting the -UseSqlSnapshot and then restored today.  It had been going for over 5 hours (longer than previous times) and has failed again with the same errors.

I did notice in the Event Viewer some errors which seem to be referring to SQL:

Unknown SQL Exception 1204 occurred. Additional error information from SQL Server is included below.

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

AND..
The Execute method of job definition Microsoft.SharePoint.Administration.SPAppInstallationJobDefinition (ID d0d977be-f5ed-440c-8e81-f5558a70a65c) threw an exception. More information is included below.

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

There was some suggestion to set the lock settings in SQL to "0" - I checked and it already is.

Maybe I'll try restore overnight again...

• Edited by kelsnz 1 hour 39 minutes ago

Hi Dean,

I am backing up and restoring to the same server so there should not be any version issues.  The account I am using to run the Restore-SPSite powershell is an SQL sys_admin and its also a farm administrator so permissions are not an issue either.

I tried yesterday a backup omitting the -UseSqlSnapshot and then restored today.  It had been going for over 5 hours (longer than previous times) and has failed again with the same errors.

I did notice in the Event Viewer some errors which seem to be referring to SQL:

Unknown SQL Exception 1204 occurred. Additional error information from SQL Server is included below.

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

AND..
The Execute method of job definition Microsoft.SharePoint.Administration.SPAppInstallationJobDefinition (ID d0d977be-f5ed-440c-8e81-f5558a70a65c) threw an exception. More information is included below.

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

There was some suggestion to set the lock settings in SQL to "0" - I checked and it already is.

Maybe I'll try restore overnight again...

• Edited by kelsnz Wednesday, May 06, 2015 6:03 AM

Hi Dean,

I am backing up and restoring to the same server so there should not be any version issues.  The account I am using to run the Restore-SPSite powershell is an SQL sys_admin and its also a farm administrator so permissions are not an issue either.

I tried yesterday a backup omitting the -UseSqlSnapshot and then restored today.  It had been going for over 5 hours (longer than previous times) and has failed again with the same errors.

I did notice in the Event Viewer some errors which seem to be referring to SQL:

Unknown SQL Exception 1204 occurred. Additional error information from SQL Server is included below.

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

AND..
The Execute method of job definition Microsoft.SharePoint.Administration.SPAppInstallationJobDefinition (ID d0d977be-f5ed-440c-8e81-f5558a70a65c) threw an exception. More information is included below.

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.

There was some suggestion to set the lock settings in SQL to "0" - I checked and it already is.

Maybe I'll try restore overnight again...

• Edited by kelsnz Wednesday, May 06, 2015 6:03 AM

*bump*

I am still not having any luck.  It definitely seems to be because the DB is very large.  It restores to about 70GB worth and then gets the error.

I'm hoping for some advice on another way around this.  How can I restore a ContentDB to a new URL?  If I can do that, then I can move-spsite to a new ContentDB after that is successful.

Hi,

About how to split SharePoint content database for your reference:

http://kancharla-sharepoint.blogspot.com/2013/07/sharepoint-split-content-database.html

http://sharepoint.stackexchange.com/questions/23466/how-to-split-a-content-database-within-site

Best Regards,

Dean Wang

Thanks for the suggestions Dean. 

The guide in the first link using STSADM, will that keep workflow history? 

I don't think the second link is an option as I need to keep workflow history.

Hi all, I am running in the similar situation where we are taking backup of recently upgraded web application in sp2013 and restoring it in the same same farm under another web application and separate content database. And getting similar error of native hr with code. We did not faced this issue in dev and stage environment and only getting it in production environment. How did you resolved your issue. Please guide

Resolved issue by upgrading content database After a little bit of time playing around, I figured out that Mount-SPContentDatabase did not indeed upgrade the content database to the SP 2013 SP1 version, it left it as is which I guess wasn't compatible with my other web application I was trying to restore to. So in order to fix this, I just had to manually run the Upgrade-SPContentDatabase command first and then back up and restore the site collection with the same command as above: upgrade-spcontentdatabase 'MYCONTENTDBNAME' Reference link http://www.khamis.net/Lists/Posts/Post.aspx?ID=329